home *** CD-ROM | disk | FTP | other *** search
- Path: engnews1.Eng.Sun.COM!taumet!clamage
- From: jcoffin@rmii.com (Jerry Coffin)
- Newsgroups: comp.std.c++
- Subject: Re: #warning
- Date: 17 Feb 1996 00:11:16 GMT
- Organization: TAEUS
- Approved: clamage@eng.sun.com (comp.std.c++)
- Message-ID: <4g366g$5il@natasha.rmii.com>
- References: <270631188wnr@pires.co.uk> <4ftd0p$c5s@engnews1.Eng.Sun.COM>
- NNTP-Posting-Host: taumet.eng.sun.com
- Content-Type: text
- X-Nntp-Posting-Host: slip22146.rmii.com
- X-Newsreader: Forte Free Agent 1.0.82
- Content-Length: 733
- X-Lines: 19
- Originator: clamage@taumet
-
- clamage@Eng.Sun.COM (Steve Clamage) wrote:
-
- [suggestion for `#warning' ]
-
- >Yes, you forgot to say how it differs from #error, which is already in the
- >draft (and in Standard C). The description of #error says only that it
- >"causes the implementation to produce a diagnostic message that includes
- >the specified sequence of preprocessing tokens."
-
- Given that #error generally _does_ cause processing to halt, it could
- simply be:
-
- "Causes the implementation to produce a diagnostic message that inlcudes
- the specified sequence of preprocessing tokens, but processing of the
- translation unit continues."
-
- I.e. whether processing halts or not isn't defined with #error, but with
- #warning, processing is explicitly defined to continue.
-
-
- [ To submit articles: Try just posting with your newsreader. If that fails,
- use mailto:std-c++@ncar.ucar.edu
- FAQ: http://reality.sgi.com/employees/austern_mti/std-c++/faq.html
- Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html
- Comments? mailto:std-c++-request@ncar.ucar.edu
- ]
-